--- file_format: mystnb kernelspec: name: python3 --- (sec-qblox-acquisition-details)= # Acquisition details This page describes important Qblox-specific behaviour of the {class}`~quantify_scheduler.operations.acquisition_library.TriggerCount`, {class}`~quantify_scheduler.operations.acquisition_library.Timetag`, {class}`~quantify_scheduler.operations.acquisition_library.TimetagTrace` and {class}`~quantify_scheduler.operations.acquisition_library.Trace` acquisition protocols. Explanations of the protocols themselves can be found in {ref}`sec-acquisition-protocols` and detailed usage examples can be found in the {ref}`sec-acquisitions` tutorials. ## Duration On all Qblox modules, the actual duration of the trigger count, timetag and timetag-trace acquisitions is **4 ns shorter** than the duration specified upon creating the operation. For example, a `TriggerCount(port="q0:res", clock="q0.ro", duration=1e-6)` will acquire data for 996 ns, but the operation will occupy 1 µs of schedule time. The start time of the actual acquisition is the same as the start time of the operation. ## Bin modes and module support Not all acquisitions work with all {class}`bin modes ` or module types. The table below lists exactly what is supported for the {class}`~quantify_scheduler.operations.acquisition_library.TriggerCount`, {class}`~quantify_scheduler.operations.acquisition_library.Timetag`, {class}`~quantify_scheduler.operations.acquisition_library.TimetagTrace` and {class}`~quantify_scheduler.operations.acquisition_library.Trace` acquisitions. For more information about the bin modes, please see the {ref}`tutorials ` and {ref}`reference guide `.
Protocol Support modules Supported bin modes
TriggerCount QRM BinMode.APPEND, BinMode.AVERAGE
QTM BinMode.APPEND
Timetag QTM BinMode.APPEND, BinMode.AVERAGE
TimetagTrace QTM BinMode.APPEND
Trace QRM, QRM-RF BinMode.AVERAGE
QTM BinMode.FIRST